Don't test SSL errors on OSX
authorAlex Crichton <alex@alexcrichton.com>
Thu, 8 Oct 2015 20:14:14 +0000 (13:14 -0700)
committerAlex Crichton <alex@alexcrichton.com>
Thu, 8 Oct 2015 20:14:14 +0000 (13:14 -0700)
Due to libgit2 perhaps using different frameworks it's a little too onerous to
test there. It's also pretty unlikely that libgit2 is configure to *not* have
SSL on OSX by mistake.

tests/test_cargo_build_auth.rs

index 9dcf1293ce81dace079a26babc271149d9437907..e7afb776507b84ea7f8359731dc9ff8a72a33416 100644 (file)
@@ -156,7 +156,10 @@ Caused by:
         errmsg = if cfg!(windows) {
             "[[..]] failed to send request: [..]\n"
         } else if cfg!(target_os = "macos") {
-            "[[..]] unexpected return value from ssl handshake [..]"
+            // OSX is difficult to tests as some builds may use
+            // Security.framework and others may use OpenSSL. In that case let's
+            // just not verify the error message here.
+            "[..]"
         } else {
             "[[..]] SSL error: [..]"
         })));